Pipeline — product requirements

Quotes — create and send quotes for devices (frigo / koelkast line) and maintenance agreements; quote lines carry per-device agreement tiers.

Pipeline — deals by stage with forecasts; a won deal hands off to Admin provisioning and creates the device's first maintenance agreement.

Partner-sold deals — deals can be attributed to a partner; winning one creates or extends that partner's coverage link with the customer (master PRT-1).

Channel chain on every deal — reseller → distributor → RiverSync, or reseller → RiverSync direct (master PRT-11). RiverSync can allocate the distributor and overrule the reseller's choice at any time — reallocation to another distributor included; every change is audited.

Direct exceptions are per deal — granted by RiverSync case by case, recorded on the deal (who granted, when); there is no standing per-partner direct flag. A deal cannot close direct without one.

Registration intake — reseller-registered deals (PAR-6) land in an intake stage for RiverSync qualification before they join the forecast funnel.

Deferred past the initial prototype — channel surface not built. Reseller tier review & grant. RiverSync owns the reseller program tier (master PRT-14, PRT-16). A channel review surface shows each reseller's balanced scorecard — certified engineers, trailing-12-month closed-deal revenue, customer satisfaction / on-time SLA — flags those eligible for the next level, and lets a RiverSync user grant · hold · downgrade the tier at the quarterly review. Each decision writes a PartnerTierReview record and emits partner.tier-changed on a grant; the reseller sees progress only (PAR-4). Tier never changes without a recorded review.

Deferred past the initial prototype — channel surface not built. Reseller→distributor conversion. RiverSync can convert a qualifying reseller — typically a strong Platinum reseller with the logistics, volume and regional coverage to supply others — into a distributor (master PRT-17). The action flips the subtype, clears the program tier (distributors hold no tier), reconciles the org's open reseller-attributed deals, and registers the distribution agreements (PRT-10) that stand it up as a distributor. Manual, RiverSync-initiated and audited (partner.subtype-changed); never self-served.

Contacts — the relationship graph. A centralized directory of the organizations and people we deal with (master SAL-1); opening a contact resolves its hierarchy (group of companies, employer, reporting line) and its wider relationships, and the graph is queryable top-down to deep-dive a prospect. The contact graph is distinct from tenancy and bridges to a customer Tenant / user only on conversion (SAL-2).

Leads — the inbound inbox. Every net-new inquiry across the six sources (online-form · telephone · showroom · trade-show · social · partner) lands here (master SAL-3, SAL-4); a sales user triages, assigns an owner, and — reusing the tier benefit — may share a lead to a partner to follow up (SAL-7). Reseller registrations (PAR-6) arrive in this queue too (supersedes the standalone intake of PIP-6).

Qualify & convert. Qualifying a lead and converting it opens an Opportunity and resolves the customer — matching an existing customer organization or creating one (master SAL-5); the conversion is one-way and recorded.

Opportunities & variants. Shape a pursuit by quantifying and comparing variants (models · quantity · maintenance tier), each with its own estimated value, and validate the one the customer will buy (master SAL-6).

Confirm to deal. The selected variant is confirmed into a Deal and seeds its quote lines (Deal.SourceOpportunity); the deal then carries the channel chain (PIP-4) through quote and close (master SAL-6, DM-50).

Activity timeline. Every email, call, visit, survey, meeting and note is logged against the contact and, where relevant, the funnel record, and shown as one blended bird's-eye timeline — activities plus journey milestones (lead captured … deal won) (master SAL-8).

Communications — the unified inbox. A central messaging surface (master SAL-9) that pulls every contact touchpoint into one threaded inbox across web form, email (sales@riversync.com), LINE, Instagram, Facebook, LinkedIn and logged phone calls, organized into the folders Inbox · Draft · Sent · Archived · Junk · Deleted. Each conversation is one channel thread tied to the contact / customer / partner it came from and to its related leads, opportunities and deals — so a sales user moves straight from a message to the relationship and its activity; sending or receiving also writes an activity (PIP-14) so the timeline stays the single history. The inbox is realtime: new inbound messages, delivery-state changes and folder moves are pushed to the client over a SignalR (WebSocket) hub and applied in place — no manual refresh — with optimistic local updates reconciled on the server ack. The list has a message search at its head and a filter control (icon + dropdown) that narrows it by channel, read status, attachments and relationship type (lead / customer / partner); the conversation actions live on a context-aware command bar — including Forward (forward the conversation) and Forward all (forward the entire thread, every message, on the same channel) alongside Archive, Junk, Mark unread and Delete — whose primary action (Reply / Send / Not junk / Restore) and Compose sit together at the bar's right edge. Distinct from customer↔support messaging. Prototype: the Communications nav group with all six folders (apps/pipeline/Inbox.html).